|
Privacy engineering is an emerging discipline within, at least, the software or information systems domain which aims to provide tools and techniques such that the engineered systems provide acceptable levels of privacy. An acceptable level of privacy is defined in terms of compliance against the functional and non-functional requirements set out through a privacy policy. == Definition and scope == The definition of privacy engineering given by NIST is:〔(【引用サイトリンク】url=http://csrc.nist.gov/projects/privacy_engineering/index.html )〕 While privacy has been developing as a legal domain, privacy engineering has only really come to the fore in recent years as the necessity of implementing said privacy laws in information systems has become a definite requirement to the deployment of such information systems. For example, IPEN〔(【引用サイトリンク】title=Background and purpose )〕 outlines their position in this respect as: Privacy engineering involves aspects such as process management, security, ontology and software engineering. The actual application of these derives from necessary legal compliances, privacy policies and `manifestos' such as Privacy-by-Design. Towards the more implementation levels, privacy engineering employs privacy enhancing technologies to enable anonymisation and de-identification of data. It however should be noted that privacy engineering requires suitable security engineering practices to be deployed, and that some privacy aspects can be implemented using security techniques. It should be noted that a privacy impact assessment is just a tool within this context and its use does not imply that privacy engineering is being practiced. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Privacy engineering」の詳細全文を読む スポンサード リンク
|